-
Notifications
You must be signed in to change notification settings - Fork 825
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat(otlp-transformer)!: introduce separate entry-points for OTLP serializers #5263
Open
pichlermarc
wants to merge
3
commits into
open-telemetry:main
Choose a base branch
from
dynatrace-oss-contrib:feat/add-transformer-entrypoints
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
feat(otlp-transformer)!: introduce separate entry-points for OTLP serializers #5263
pichlermarc
wants to merge
3
commits into
open-telemetry:main
from
dynatrace-oss-contrib:feat/add-transformer-entrypoints
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
pichlermarc
force-pushed
the
feat/add-transformer-entrypoints
branch
from
December 13, 2024 12:45
ec2720d
to
176b776
Compare
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #5263 +/- ##
=======================================
Coverage 94.63% 94.63%
=======================================
Files 323 323
Lines 8083 8083
Branches 1643 1643
=======================================
Hits 7649 7649
Misses 434 434
|
pichlermarc
force-pushed
the
feat/add-transformer-entrypoints
branch
from
December 13, 2024 13:03
176b776
to
2e74b8a
Compare
pichlermarc
changed the title
feat(otlp-transformer)!: introduce separate entry-points for OTLP serializers, switch to factory functions
feat(otlp-transformer)!: introduce separate entry-points for OTLP serializers
Dec 13, 2024
pichlermarc
force-pushed
the
feat/add-transformer-entrypoints
branch
2 times, most recently
from
December 13, 2024 13:23
2a53f1b
to
8c1c6be
Compare
2 tasks
pichlermarc
force-pushed
the
feat/add-transformer-entrypoints
branch
from
December 13, 2024 16:27
8c1c6be
to
7aca149
Compare
10 tasks
raphael-theriault-swi
approved these changes
Dec 17, 2024
pichlermarc
commented
Dec 19, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Which problem is this PR solving?
This is the second-to-last breaking PR for
@opentelemetry/otlp-transformer
before marking the package as stable (#4582). This solves some issues with rollup, that warns even for code that is dead in the end-user's app. See #5096, #4987.This PR adds entry points for each signal, each signal gets an entry point for
protobuf
andjson
to address #5096 and #4987The new entrypoint structure is:
-
/signal
,/signal/protobuf
,signal/json
- experimental signals are prefixed by
experimental/
to allow us marking the package stable before the experimental signals are - the spec moves quicker than we do, so I expect there to always be one that is not stableCloses #5216
Closes #4584
Fixes #5096
Partially addresses #4987
Type of change
How Has This Been Tested?